Release Notes 7.8.0.1
(Released September 2024)
Overview
This release of Resolve Actions Pro aims to resolve issues found since release 7.8. It does not introduce new features or breaking changes.
Resolved Issues
The following issues have been resolved with this Actions Pro version.
| Ticket | Summary |
|---|---|
| 45047 | Fixed invalid PARAMS causing Unacknowledged messages |
| 43844 | Fixed error where action task properties were not displaying correctly |
| n/a | Fixed issue where ServiceNow gateway failed to read some configurations |
| 45653 | Fixed issue where sys_updated_on sometimes did not update |
| 45937 | Fixed issue where HTTP Gateway configurations on the default port did not consistently take effect |
| 45886 | Fixed an error in DB Gateway for some Oracle DB connections |
| 45915 | Updates multiple jars to address vulnerabilities |
| 46038 | Updates the Spring Framework to resolve vulnerabilities |
| 46103 | Fixed issue where Gateway Builder Run Test failed with 500 error |
| 46104 | Fixed issue where Gateway Accessible AT Properties were not loading in Builder Gateway |
| n/a | Fixed issue where AT Properties were not displaying in Package Manager |
| 45919 | Fixed issue where some AT Properties were missing from the Content Browser |
| 45253 | Fixed performance metrics being unavailable |
| 45915 | Fixed scan of AT Properties on Namespace export only picking up one property |
| 46054 | Fixed issue where some AT Properties were missing from Content Browser |
| 45253 | Fixed issue where RSLog failed to start |
| 46337 | Changed Threadpool availability to HTTP Gateway to prevent resource blocking |
| 46095 | Fixed issue where OAuth config for default HTTP Gateway port was not deploying correctly |
| 46686 | Fixed issue where LSM configurations were applied to static indices |
| 46645 | Fixed issue where Assign Groups/Roles buttons on the Users page was not clearing cache correctly |
| 46725 | Fixed error writing Events to ES with large processState values |
| 45764 | Fixed issue where Login sessions from SAML used hard coded timeout instead of configured timeout |
| n/a | Updated JDK logic for Windows update |